Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64cec6f00fe5236262d8e7c4add1bbd22933be940601ff1d38f4fcb58ba1427

Tx prefix hash: be0da722390e85adbd306c7506181bf96f79d6691463d737d2cf3384dbb5d2ca
Tx public key: 7b215cdc76b6071dfdb2980aaa3a679c1699d81ef6698aa1d0b714da2a53c3f0
Timestamp: 1719477614 Timestamp [UCT]: 2024-06-27 08:40:14 Age [y:d:h:m:s]: 00:319:13:17:44
Block: 1053219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228368 RingCT/type: yes/0
Extra: 017b215cdc76b6071dfdb2980aaa3a679c1699d81ef6698aa1d0b714da2a53c3f002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 658d7cf5409e6b09871fe02b139aeca36c42d080c7393fc1a7b9b029a90916e3 0.600000000000 1523566 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": 1053229, "vin": [ { "gen": { "height": 1053219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "658d7cf5409e6b09871fe02b139aeca36c42d080c7393fc1a7b9b029a90916e3" } } ], "extra": [ 1, 123, 33, 92, 220, 118, 182, 7, 29, 253, 178, 152, 10, 170, 58, 103, 156, 22, 153, 216, 30, 246, 105, 138, 161, 208, 183, 20, 218, 42, 83, 195, 240, 2, 17, 0, 0, 0, 1, 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