Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9f6fffe504fdde060928fcf48a75bdf15899cb639a89a2e3342059b8857d2b7

Tx prefix hash: 4b6f504bd8476d8b42465f3683bf72f05d2d0da0a2fd4e062c6e3bb4877f1eda
Tx public key: 255990d18ac3864f6e086462d359ca7c7a3def599fd74a0c5840ef6610374117
Timestamp: 1749510224 Timestamp [UCT]: 2025-06-09 23:03:44 Age [y:d:h:m:s]: 00:157:21:36:39
Block: 1301658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110535 RingCT/type: yes/0
Extra: 01255990d18ac3864f6e086462d359ca7c7a3def599fd74a0c5840ef66103741170211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df32de28f49f0c0791913ed5f03470579c8a0e8f9fa5e20925f3e68c4291426 0.600000000000 1789219 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": 1301668, "vin": [ { "gen": { "height": 1301658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df32de28f49f0c0791913ed5f03470579c8a0e8f9fa5e20925f3e68c4291426" } } ], "extra": [ 1, 37, 89, 144, 209, 138, 195, 134, 79, 110, 8, 100, 98, 211, 89, 202, 124, 122, 61, 239, 89, 159, 215, 74, 12, 88, 64, 239, 102, 16, 55, 65, 23, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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