Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb9ea4e855db853ea7cdb7dcf35e7b7bea020b7192e288fa837edabce440693

Tx prefix hash: 8f8462e79f202f6041e0662caf8f442ad1adb4a0d5e2f4cad512e7e92430b1a0
Tx public key: 76d45172c0b6bc466de9eb0dc6f38834d662486fe3a8d2c87d494358444db546
Timestamp: 1724895823 Timestamp [UCT]: 2024-08-29 01:43:43 Age [y:d:h:m:s]: 00:177:13:15:55
Block: 1098143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126703 RingCT/type: yes/0
Extra: 0176d45172c0b6bc466de9eb0dc6f38834d662486fe3a8d2c87d494358444db54602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb70d70409d4719a13413a21d9a5da415899e8c9deb5c5f833229ce7a28e3ad 0.600000000000 1573758 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": 1098153, "vin": [ { "gen": { "height": 1098143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb70d70409d4719a13413a21d9a5da415899e8c9deb5c5f833229ce7a28e3ad" } } ], "extra": [ 1, 118, 212, 81, 114, 192, 182, 188, 70, 109, 233, 235, 13, 198, 243, 136, 52, 214, 98, 72, 111, 227, 168, 210, 200, 125, 73, 67, 88, 68, 77, 181, 70, 2, 17, 0, 0, 0, 1, 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