Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd85e8f3430bab91a3fca9a00709fd770b53c69dc9289a8ebe84e4c8cb84bb37

Tx prefix hash: f67e9939ea4e8f4164c7b35de31003f4764388fd20e3963c8182f7e0715f4dec
Tx public key: 81edb01aec953e0b64b17c18c57275d081e37bd747c3aa129c8a941c9938d214
Timestamp: 1721297312 Timestamp [UCT]: 2024-07-18 10:08:32 Age [y:d:h:m:s]: 00:262:13:19:53
Block: 1068329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187537 RingCT/type: yes/0
Extra: 0181edb01aec953e0b64b17c18c57275d081e37bd747c3aa129c8a941c9938d214021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe5f26dd826487d2e5e8e087a4ce87b17b6350b96815fefb344c1dea12dcfaf 0.600000000000 1539406 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": 1068339, "vin": [ { "gen": { "height": 1068329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe5f26dd826487d2e5e8e087a4ce87b17b6350b96815fefb344c1dea12dcfaf" } } ], "extra": [ 1, 129, 237, 176, 26, 236, 149, 62, 11, 100, 177, 124, 24, 197, 114, 117, 208, 129, 227, 123, 215, 71, 195, 170, 18, 156, 138, 148, 28, 153, 56, 210, 20, 2, 17, 0, 0, 0, 4, 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