Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5bedd4d2b41fd2a10bf7199fc5c48ac23c584b76f6d689134c99249d2bd2453d

Tx prefix hash: 5752dcd051a046533317324a31ae85b0fc802eea9eefc18dab8b7d58450f94cf
Tx public key: 48e84a7b97569591f0e41883f2564696fe30e5c04d7574e89bf444f3f543dbc5
Timestamp: 1647696901 Timestamp [UCT]: 2022-03-19 13:35:01 Age [y:d:h:m:s]: 03:040:22:28:15
Block: 461844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 809439 RingCT/type: yes/0
Extra: 0148e84a7b97569591f0e41883f2564696fe30e5c04d7574e89bf444f3f543dbc5021100000004bf7ee4e7000000000000000000

1 output(s) for total of 18.101700242000 dcy

stealth address amount amount idx
00: 7f3fe0462db19fcdd22bab1179d8d1d92f1637b42dcf3812ef7024d9f60e6c0b 18.101700242000 879169 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 461854, "vin": [ { "gen": { "height": 461844 } } ], "vout": [ { "amount": 18101700242, "target": { "key": "7f3fe0462db19fcdd22bab1179d8d1d92f1637b42dcf3812ef7024d9f60e6c0b" } } ], "extra": [ 1, 72, 232, 74, 123, 151, 86, 149, 145, 240, 228, 24, 131, 242, 86, 70, 150, 254, 48, 229, 192, 77, 117, 116, 232, 155, 244, 68, 243, 245, 67, 219, 197, 2, 17, 0, 0, 0, 4, 191, 126, 228, 231, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8