Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cccdd57c11359b6ba4393392ef8acaa0a7cc8fa0b39b24a361357cd925e59cf

Tx prefix hash: 95fba6e2d8bfae6511200b1e53d76da612be75152a29878eae7bc5f8e03d8636
Tx public key: aded9eae2a76373f215ba58e8c6d92ddf6a7942cf4dfb467eda3abedaa324e54
Timestamp: 1735304155 Timestamp [UCT]: 2024-12-27 12:55:55 Age [y:d:h:m:s]: 00:313:12:54:08
Block: 1184300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221581 RingCT/type: yes/0
Extra: 01aded9eae2a76373f215ba58e8c6d92ddf6a7942cf4dfb467eda3abedaa324e540211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfc0aee701ef2f372b5abb618f0abcf5f7a9c77648f9450a06b77184ef06e2f0 0.600000000000 1670757 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": 1184310, "vin": [ { "gen": { "height": 1184300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfc0aee701ef2f372b5abb618f0abcf5f7a9c77648f9450a06b77184ef06e2f0" } } ], "extra": [ 1, 173, 237, 158, 174, 42, 118, 55, 63, 33, 91, 165, 142, 140, 109, 146, 221, 246, 167, 148, 44, 244, 223, 180, 103, 237, 163, 171, 237, 170, 50, 78, 84, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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