Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35dcc32b7f9b0c5fa9246f09333dc6b6f45b6b0a94ceb0a3afdba47dc2f52e33

Tx prefix hash: 7aca2210b3d3ec1c0e9a8ef05e7fef64e793c7d421379aaefaa12a74490cb195
Tx public key: ff2bc9f43b74d80d040a4817b5123dd7b2b414f5b3de2273e5bac738dd977584
Timestamp: 1648627001 Timestamp [UCT]: 2022-03-30 07:56:41 Age [y:d:h:m:s]: 02:271:20:32:49
Block: 469442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 713912 RingCT/type: yes/0
Extra: 01ff2bc9f43b74d80d040a4817b5123dd7b2b414f5b3de2273e5bac738dd97758402110000000c4a0f5013000000000000000000

1 output(s) for total of 17.082208941000 dcy

stealth address amount amount idx
00: 56a53d31331b4d1b317314497538b6d38c7aa8a18bc37cc8a9123fc1e4ebd4b6 17.082208941000 888390 of 0

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": 469452, "vin": [ { "gen": { "height": 469442 } } ], "vout": [ { "amount": 17082208941, "target": { "key": "56a53d31331b4d1b317314497538b6d38c7aa8a18bc37cc8a9123fc1e4ebd4b6" } } ], "extra": [ 1, 255, 43, 201, 244, 59, 116, 216, 13, 4, 10, 72, 23, 181, 18, 61, 215, 178, 180, 20, 245, 179, 222, 34, 115, 229, 186, 199, 56, 221, 151, 117, 132, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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