Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85206cf02a44c9eac64cd917e9d03b397c46781e503ffa271943e1e9ee8f13b8

Tx prefix hash: 6341f02670856e46f3669441e403859a0a02928c6be9b9b8d72bee850066e836
Tx public key: 45cfe19d7779f3ac400a9e58aac67e1ccb6094d25b2dfd6a21a24d8f0573ef4c
Timestamp: 1705980667 Timestamp [UCT]: 2024-01-23 03:31:07 Age [y:d:h:m:s]: 01:054:07:45:52
Block: 941300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299937 RingCT/type: yes/0
Extra: 0145cfe19d7779f3ac400a9e58aac67e1ccb6094d25b2dfd6a21a24d8f0573ef4c02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32db554e6ec78e4a147181a498ce12e93e4269df8ecf103f978170ecca688c5a 0.600000000000 1399446 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": 941310, "vin": [ { "gen": { "height": 941300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32db554e6ec78e4a147181a498ce12e93e4269df8ecf103f978170ecca688c5a" } } ], "extra": [ 1, 69, 207, 225, 157, 119, 121, 243, 172, 64, 10, 158, 88, 170, 198, 126, 28, 203, 96, 148, 210, 91, 45, 253, 106, 33, 162, 77, 143, 5, 115, 239, 76, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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