Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec455a05824d9b3a0bd363d806e2085c416f8396dd97d538ada4993991a9e0b

Tx prefix hash: 306c494c8067feb0961aeafb1600641c0b2ca85861b5d60a5cb051445d6462d2
Tx public key: d78f8dad487cb0c057967d83cfad608d5df89b9e88cdbaf26fafacc80ae84120
Timestamp: 1723325164 Timestamp [UCT]: 2024-08-10 21:26:04 Age [y:d:h:m:s]: 01:101:05:56:44
Block: 1085127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330842 RingCT/type: yes/0
Extra: 01d78f8dad487cb0c057967d83cfad608d5df89b9e88cdbaf26fafacc80ae84120021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4c47ff86957ca3c01ad64601c9d6fd96e681ceea3b02a9c3c061d56c361ceab 0.600000000000 1559636 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": 1085137, "vin": [ { "gen": { "height": 1085127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4c47ff86957ca3c01ad64601c9d6fd96e681ceea3b02a9c3c061d56c361ceab" } } ], "extra": [ 1, 215, 143, 141, 173, 72, 124, 176, 192, 87, 150, 125, 131, 207, 173, 96, 141, 93, 248, 155, 158, 136, 205, 186, 242, 111, 175, 172, 200, 10, 232, 65, 32, 2, 17, 0, 0, 0, 3, 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