Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0351f150417e1c395a7c1a11279e2e7511c6d8fa5cd8af7bd9396aa9286a30

Tx prefix hash: 6717ddccc3e73ec7442b2c9216c1aa771a59e9d76774d2411ceebcdcf3b644a3
Tx public key: 00642b984e93bf35e5658cf541fe1096d422172e08118c2f08082edc43a8e260
Timestamp: 1728985119 Timestamp [UCT]: 2024-10-15 09:38:39 Age [y:d:h:m:s]: 00:228:12:41:11
Block: 1132058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163144 RingCT/type: yes/0
Extra: 0100642b984e93bf35e5658cf541fe1096d422172e08118c2f08082edc43a8e26002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51fe3a5561c3b85a852e7def46fb5ce87828a1c840c438831ea9d90c7f9c61db 0.600000000000 1614967 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": 1132068, "vin": [ { "gen": { "height": 1132058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51fe3a5561c3b85a852e7def46fb5ce87828a1c840c438831ea9d90c7f9c61db" } } ], "extra": [ 1, 0, 100, 43, 152, 78, 147, 191, 53, 229, 101, 140, 245, 65, 254, 16, 150, 212, 34, 23, 46, 8, 17, 140, 47, 8, 8, 46, 220, 67, 168, 226, 96, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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