Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8273b068a8f34fa0c98bf4c004f0c4162ebca14ca8345f6448b9aa7b0406cebd

Tx prefix hash: 130dd0a75bf0653521baba9c202889629b62c8eaed4082807ad84ed7c38a6f11
Tx public key: 80852e89f2bd6e44f52200cc5d7cbd4bc5493e724c324387d6d7517354080d2e
Timestamp: 1711728927 Timestamp [UCT]: 2024-03-29 16:15:27 Age [y:d:h:m:s]: 00:226:17:53:30
Block: 988999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162300 RingCT/type: yes/0
Extra: 0180852e89f2bd6e44f52200cc5d7cbd4bc5493e724c324387d6d7517354080d2e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2906557c42011ab5728dfca4c21c00adf5bdce06107d5d30c5b224a8e64c189c 0.600000000000 1449290 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": 989009, "vin": [ { "gen": { "height": 988999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2906557c42011ab5728dfca4c21c00adf5bdce06107d5d30c5b224a8e64c189c" } } ], "extra": [ 1, 128, 133, 46, 137, 242, 189, 110, 68, 245, 34, 0, 204, 93, 124, 189, 75, 197, 73, 62, 114, 76, 50, 67, 135, 214, 215, 81, 115, 84, 8, 13, 46, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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