Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfde0995a0d56f624b5b8850eae1069ad8d7486a8f854c68cb4263d3d7878ad3

Tx prefix hash: 4fafa52ce686014441fac384cae2a72b99ca7ee5ebede3c4c0aef0bae1ef52c4
Tx public key: d097536fc3dc29137dc5fbd6e1ef04fd6faf9685633813217b0adbc00eb4d08e
Timestamp: 1722086594 Timestamp [UCT]: 2024-07-27 13:23:14 Age [y:d:h:m:s]: 01:073:13:00:19
Block: 1074853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311013 RingCT/type: yes/0
Extra: 01d097536fc3dc29137dc5fbd6e1ef04fd6faf9685633813217b0adbc00eb4d08e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 558ea7375598983d41df4473f08cae04ebaf940f24a99b7a95295f30fac51dfa 0.600000000000 1547372 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": 1074863, "vin": [ { "gen": { "height": 1074853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558ea7375598983d41df4473f08cae04ebaf940f24a99b7a95295f30fac51dfa" } } ], "extra": [ 1, 208, 151, 83, 111, 195, 220, 41, 19, 125, 197, 251, 214, 225, 239, 4, 253, 111, 175, 150, 133, 99, 56, 19, 33, 123, 10, 219, 192, 14, 180, 208, 142, 2, 17, 0, 0, 0, 5, 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