Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4866a078005d6729e34c7f44a5cb9f60709b0811cf4998f10b17aaa1650921c

Tx prefix hash: 63600c00b85b694d70a2e89f11df8477cabd08e923969d2673465a7cb5bc121a
Tx public key: 667c5ee18e82d3c4746a1a711e1542b3deb8d4b63c9b89af0b8eb54ba24c6422
Timestamp: 1709173642 Timestamp [UCT]: 2024-02-29 02:27:22 Age [y:d:h:m:s]: 01:265:15:18:26
Block: 967805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448586 RingCT/type: yes/0
Extra: 01667c5ee18e82d3c4746a1a711e1542b3deb8d4b63c9b89af0b8eb54ba24c64220211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b34d49e4225b47c5190b14ab5016871a00f99ccaaf2b04ae7b852eb664dc5e86 0.600000000000 1427590 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": 967815, "vin": [ { "gen": { "height": 967805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b34d49e4225b47c5190b14ab5016871a00f99ccaaf2b04ae7b852eb664dc5e86" } } ], "extra": [ 1, 102, 124, 94, 225, 142, 130, 211, 196, 116, 106, 26, 113, 30, 21, 66, 179, 222, 184, 212, 182, 60, 155, 137, 175, 11, 142, 181, 75, 162, 76, 100, 34, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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