Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9edaac4936489ff574a05936c4404255d9f523c337fee88f4c0fda02535aa589

Tx prefix hash: cbf02d630517374b86ca9bb346e03bcffb41dfea730ecc8e1dc7d4f1a764dc75
Tx public key: 6b0eda4986b248f1dd9e712eb5572322c89ab2c4d6bcf4724bc6ae495e4253ef
Timestamp: 1736544724 Timestamp [UCT]: 2025-01-10 21:32:04 Age [y:d:h:m:s]: 00:115:23:48:53
Block: 1194580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82696 RingCT/type: yes/0
Extra: 016b0eda4986b248f1dd9e712eb5572322c89ab2c4d6bcf4724bc6ae495e4253ef02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 276e92a26d5ce1e5dbf813ca4136b44522a89c8ca8f47182ddcdaeaa0b4fff25 0.600000000000 1681157 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": 1194590, "vin": [ { "gen": { "height": 1194580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "276e92a26d5ce1e5dbf813ca4136b44522a89c8ca8f47182ddcdaeaa0b4fff25" } } ], "extra": [ 1, 107, 14, 218, 73, 134, 178, 72, 241, 221, 158, 113, 46, 181, 87, 35, 34, 200, 154, 178, 196, 214, 188, 244, 114, 75, 198, 174, 73, 94, 66, 83, 239, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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