Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563c6e0a9eeb24743d4130cd69ae401a8766a9dc000ffaab8ceaf31a8b1c46ae

Tx prefix hash: 5b2bf4f733545c110e90a2591c7ab0354e7b5cb84fe3da5b8ae7a95beeab1a23
Tx public key: 6545c1869174c0b77e8904b4140218c22b0371048253fa2802cc702d460a18cd
Timestamp: 1694273758 Timestamp [UCT]: 2023-09-09 15:35:58 Age [y:d:h:m:s]: 01:212:17:49:32
Block: 844455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413155 RingCT/type: yes/0
Extra: 016545c1869174c0b77e8904b4140218c22b0371048253fa2802cc702d460a18cd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.977169943000 dcy

stealth address amount amount idx
00: 12a789b601ad1f2dceb6b341e03e6569965a28745e2c64e59acbabe82ce245d3 0.977169943000 1297765 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": 844465, "vin": [ { "gen": { "height": 844455 } } ], "vout": [ { "amount": 977169943, "target": { "key": "12a789b601ad1f2dceb6b341e03e6569965a28745e2c64e59acbabe82ce245d3" } } ], "extra": [ 1, 101, 69, 193, 134, 145, 116, 192, 183, 126, 137, 4, 180, 20, 2, 24, 194, 43, 3, 113, 4, 130, 83, 250, 40, 2, 204, 112, 45, 70, 10, 24, 205, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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