Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2e188d3639cf8879e4a575e970dee5c9bf18df0a70b86e26ce14cb8564ddd8

Tx prefix hash: b776862a9cc758744be7580119c34d4467fb16d08d3b652cfffa8740f4b7c0d2
Tx public key: 94c506a8530de93d443afed0b1350629140afd85c5aae45a623e88aa8367f629
Timestamp: 1714899496 Timestamp [UCT]: 2024-05-05 08:58:16 Age [y:d:h:m:s]: 01:028:13:41:42
Block: 1015280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281361 RingCT/type: yes/0
Extra: 0194c506a8530de93d443afed0b1350629140afd85c5aae45a623e88aa8367f62902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8c7f0736a364c5f8e4ac866408c14186568e75560cca2569a89a9e1546f67b7 0.600000000000 1478599 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": 1015290, "vin": [ { "gen": { "height": 1015280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8c7f0736a364c5f8e4ac866408c14186568e75560cca2569a89a9e1546f67b7" } } ], "extra": [ 1, 148, 197, 6, 168, 83, 13, 233, 61, 68, 58, 254, 208, 177, 53, 6, 41, 20, 10, 253, 133, 197, 170, 228, 90, 98, 62, 136, 170, 131, 103, 246, 41, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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