Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44739c880367832d3d3e298c6e508ea7a701bd0b295d3f090e697e268779023d

Tx prefix hash: f774885bb1bfa67eaeb1565161b8c09ed46d76768a39bac37a77ff0a55e39921
Tx public key: 811c6c633186317c041af595f028bd8c8254cc481dff9d782c49b058f524d3a8
Timestamp: 1710356694 Timestamp [UCT]: 2024-03-13 19:04:54 Age [y:d:h:m:s]: 01:035:20:28:41
Block: 977628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286610 RingCT/type: yes/0
Extra: 01811c6c633186317c041af595f028bd8c8254cc481dff9d782c49b058f524d3a802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da8d24c50ad8b8dad0d334417915bc8a22696a7000a518a69247ef518f2cb3c 0.600000000000 1437631 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": 977638, "vin": [ { "gen": { "height": 977628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da8d24c50ad8b8dad0d334417915bc8a22696a7000a518a69247ef518f2cb3c" } } ], "extra": [ 1, 129, 28, 108, 99, 49, 134, 49, 124, 4, 26, 245, 149, 240, 40, 189, 140, 130, 84, 204, 72, 29, 255, 157, 120, 44, 73, 176, 88, 245, 36, 211, 168, 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