Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da310294797b9481f67c6373eeb1c2822cc9f96ed4b92c50a21c56e23657dd8b

Tx prefix hash: 6af5e4dfa561ac139b800ac4e097e6c89f0416c1b904f91da047c0a22963dcc5
Tx public key: 660d151f2f08e6ab2d4ca48f0e95805b24aefd1a969a492206a0772ec6f29d78
Timestamp: 1723864915 Timestamp [UCT]: 2024-08-17 03:21:55 Age [y:d:h:m:s]: 00:227:23:45:50
Block: 1089604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162795 RingCT/type: yes/0
Extra: 01660d151f2f08e6ab2d4ca48f0e95805b24aefd1a969a492206a0772ec6f29d7802110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 748f781a6ada81cd6f316c0e164d995ae50fcccfb4e256b8eec2bfb827eaa04c 0.600000000000 1564227 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": 1089614, "vin": [ { "gen": { "height": 1089604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "748f781a6ada81cd6f316c0e164d995ae50fcccfb4e256b8eec2bfb827eaa04c" } } ], "extra": [ 1, 102, 13, 21, 31, 47, 8, 230, 171, 45, 76, 164, 143, 14, 149, 128, 91, 36, 174, 253, 26, 150, 154, 73, 34, 6, 160, 119, 46, 198, 242, 157, 120, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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