Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71062f973d9cb156d7b9b84adbe8b1ad44d8e40d5b5ee6dd62b0a421c334acc1

Tx prefix hash: f7293989c9db1536894b651c4a693f50e8987076405e63674f287f349bdc8410
Tx public key: bf68d3bd93873b2400488821f4b64b6b13f437630cccbefd7d924130f7ec8d49
Timestamp: 1726789547 Timestamp [UCT]: 2024-09-19 23:45:47 Age [y:d:h:m:s]: 00:220:13:23:59
Block: 1113841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157481 RingCT/type: yes/0
Extra: 01bf68d3bd93873b2400488821f4b64b6b13f437630cccbefd7d924130f7ec8d49021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a0ceb72ab50c1f4eee0548a9266d94b98eec2ff0395642773e930834264ed7 0.600000000000 1593638 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": 1113851, "vin": [ { "gen": { "height": 1113841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a0ceb72ab50c1f4eee0548a9266d94b98eec2ff0395642773e930834264ed7" } } ], "extra": [ 1, 191, 104, 211, 189, 147, 135, 59, 36, 0, 72, 136, 33, 244, 182, 75, 107, 19, 244, 55, 99, 12, 204, 190, 253, 125, 146, 65, 48, 247, 236, 141, 73, 2, 17, 0, 0, 0, 6, 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