Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075064a7f10853fb6de7ba79a1001b3b5327516f21b99dc753444276f83a22ac

Tx prefix hash: 203f0ce2073a29a00d4dfea7e99910dc2ebd9a23d42665fb8f6b8a48733d64f3
Tx public key: ef8f30cca027e35e520a0a2b961200d4383cfaf1e47704ed1a86480d65d28ff8
Timestamp: 1672704686 Timestamp [UCT]: 2023-01-03 00:11:26 Age [y:d:h:m:s]: 02:112:13:04:59
Block: 666321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602135 RingCT/type: yes/0
Extra: 01ef8f30cca027e35e520a0a2b961200d4383cfaf1e47704ed1a86480d65d28ff802110000000152542ceb000000000000000000

1 output(s) for total of 3.803661727000 dcy

stealth address amount amount idx
00: a96aa416c3a0e575bd79b0ba3a43eab725dc7e60ea22c9cf44b0599eff6cdf2f 3.803661727000 1107428 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": 666331, "vin": [ { "gen": { "height": 666321 } } ], "vout": [ { "amount": 3803661727, "target": { "key": "a96aa416c3a0e575bd79b0ba3a43eab725dc7e60ea22c9cf44b0599eff6cdf2f" } } ], "extra": [ 1, 239, 143, 48, 204, 160, 39, 227, 94, 82, 10, 10, 43, 150, 18, 0, 212, 56, 60, 250, 241, 228, 119, 4, 237, 26, 134, 72, 13, 101, 210, 143, 248, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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