Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391f0cbf6bb0d8248dff9b0b0ca70b1db6fce9ea892f4706108207e36e581535

Tx prefix hash: 1f39f87117952a9b694ce065af3ddbc4e882964b11f60e4a33dc4caa9af0a3fc
Tx public key: bb109615ca5861d80645efd19dc4c1d57255d7c71232fb96e63da85874020e7e
Timestamp: 1726889871 Timestamp [UCT]: 2024-09-21 03:37:51 Age [y:d:h:m:s]: 00:197:11:57:07
Block: 1114677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140959 RingCT/type: yes/0
Extra: 01bb109615ca5861d80645efd19dc4c1d57255d7c71232fb96e63da85874020e7e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6f62b5ba87b80baee7289ef55d8b8eee040cb7035d3ed89472a2eb6bc1fc706 0.600000000000 1594542 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": 1114687, "vin": [ { "gen": { "height": 1114677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6f62b5ba87b80baee7289ef55d8b8eee040cb7035d3ed89472a2eb6bc1fc706" } } ], "extra": [ 1, 187, 16, 150, 21, 202, 88, 97, 216, 6, 69, 239, 209, 157, 196, 193, 213, 114, 85, 215, 199, 18, 50, 251, 150, 230, 61, 168, 88, 116, 2, 14, 126, 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