Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed791722e3085f4baf47fce95573f6b290b79caca20fffc5b69703c687b780b3

Tx prefix hash: ec8620241d1310b7c1919c2946865cd5125e7127af62fbeeac5f0ef8f3c3063b
Tx public key: 5fe21de86bbff1c4e18c46996bb2b84ef3cb1d792a87a4e511d43262063c6ecd
Timestamp: 1700249938 Timestamp [UCT]: 2023-11-17 19:38:58 Age [y:d:h:m:s]: 01:104:22:47:25
Block: 893814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336161 RingCT/type: yes/0
Extra: 015fe21de86bbff1c4e18c46996bb2b84ef3cb1d792a87a4e511d43262063c6ecd021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.670537654000 dcy

stealth address amount amount idx
00: 0d7a879492108dc68ce7d51223d4e80586e26b7205814497be5bcd48f29427fa 0.670537654000 1349999 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": 893824, "vin": [ { "gen": { "height": 893814 } } ], "vout": [ { "amount": 670537654, "target": { "key": "0d7a879492108dc68ce7d51223d4e80586e26b7205814497be5bcd48f29427fa" } } ], "extra": [ 1, 95, 226, 29, 232, 107, 191, 241, 196, 225, 140, 70, 153, 107, 178, 184, 78, 243, 203, 29, 121, 42, 135, 164, 229, 17, 212, 50, 98, 6, 60, 110, 205, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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