Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634c8544bc0dec0b1980dc3f2bc0e5cb7f764e9aaa1d36b03ffbde0463cf829d

Tx prefix hash: 74cda92670755afa1c25eec6078e4d90f5cba67a430a5a33ad651ebcbf0026be
Tx public key: 368127e67d26777eb0dc1e1ac21c757bcd9eae549b6721d60df6a1e7ba408307
Timestamp: 1683392325 Timestamp [UCT]: 2023-05-06 16:58:45 Age [y:d:h:m:s]: 01:359:23:35:11
Block: 754320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518515 RingCT/type: yes/0
Extra: 01368127e67d26777eb0dc1e1ac21c757bcd9eae549b6721d60df6a1e7ba40830702110000000433af99f4000000000000000000

1 output(s) for total of 1.943680617000 dcy

stealth address amount amount idx
00: c510453e66dffe669f41c2aba88d49a272a925d2d18a5d0dbc92727ca3bf373e 1.943680617000 1202573 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": 754330, "vin": [ { "gen": { "height": 754320 } } ], "vout": [ { "amount": 1943680617, "target": { "key": "c510453e66dffe669f41c2aba88d49a272a925d2d18a5d0dbc92727ca3bf373e" } } ], "extra": [ 1, 54, 129, 39, 230, 125, 38, 119, 126, 176, 220, 30, 26, 194, 28, 117, 123, 205, 158, 174, 84, 155, 103, 33, 214, 13, 246, 161, 231, 186, 64, 131, 7, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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