Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 154bf5368c2cb8707b7201ae19be7a703e2871247a0ce83f6d6860273d23d850

Tx prefix hash: 93231bb2c3289608250fd9bb1bd479589881949b64d1949ffd14e574803e5a47
Tx public key: 4e44517a32d608224bae00f8e7bfe888b18d3b6dfc5858b5d22d20828a2aaf5b
Timestamp: 1707424641 Timestamp [UCT]: 2024-02-08 20:37:21 Age [y:d:h:m:s]: 01:054:15:48:29
Block: 953291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300113 RingCT/type: yes/0
Extra: 014e44517a32d608224bae00f8e7bfe888b18d3b6dfc5858b5d22d20828a2aaf5b02110000000e10a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e58838b1a7cb459e2d8ba3791a1dcb95738a0a28ac203d01e5f3cea51021ddf8 0.600000000000 1412483 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": 953301, "vin": [ { "gen": { "height": 953291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e58838b1a7cb459e2d8ba3791a1dcb95738a0a28ac203d01e5f3cea51021ddf8" } } ], "extra": [ 1, 78, 68, 81, 122, 50, 214, 8, 34, 75, 174, 0, 248, 231, 191, 232, 136, 177, 141, 59, 109, 252, 88, 88, 181, 210, 45, 32, 130, 138, 42, 175, 91, 2, 17, 0, 0, 0, 14, 16, 161, 116, 143, 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