Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c91ff542a132c24208168d6a150d1f4f9b3873707ae4a189111cc2fd7719e9

Tx prefix hash: 44d426bb1554ad558e7d2bfa858dc00dadce0cc8a51e6d2a2288ba08a5396034
Tx public key: 9d9c380f2d58031c3406587c2b8c6bbe0d085e4d825008c633cf746bed81e879
Timestamp: 1708148870 Timestamp [UCT]: 2024-02-17 05:47:50 Age [y:d:h:m:s]: 01:045:10:42:47
Block: 959297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293514 RingCT/type: yes/0
Extra: 019d9c380f2d58031c3406587c2b8c6bbe0d085e4d825008c633cf746bed81e87902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71264094c1029dfae241cb1817a30e5c1b6b67c5d940a49a79e4872f7fb7b37d 0.600000000000 1418832 of 15

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": 959307, "vin": [ { "gen": { "height": 959297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71264094c1029dfae241cb1817a30e5c1b6b67c5d940a49a79e4872f7fb7b37d" } } ], "extra": [ 1, 157, 156, 56, 15, 45, 88, 3, 28, 52, 6, 88, 124, 43, 140, 107, 190, 13, 8, 94, 77, 130, 80, 8, 198, 51, 207, 116, 107, 237, 129, 232, 121, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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