Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c84be12f6bd54089ebf9c9253e5b1b3106dc137bc736ff319f034eaff6ddfdb

Tx prefix hash: 27ec3da675b0c95c1db341d8f80e05f833e95b726c702d0426c9735182a4cd36
Tx public key: 544da874254803e67c233794ed75a01213a5b4b7ddb5d0f9c2c1339bf2af7c3b
Timestamp: 1723367672 Timestamp [UCT]: 2024-08-11 09:14:32 Age [y:d:h:m:s]: 00:240:19:13:49
Block: 1085477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171978 RingCT/type: yes/0
Extra: 01544da874254803e67c233794ed75a01213a5b4b7ddb5d0f9c2c1339bf2af7c3b021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a7994e2bfdafeffe597ce44ea51e8b0becd3808856df54cf5e164a502a4d866 0.600000000000 1560062 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": 1085487, "vin": [ { "gen": { "height": 1085477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a7994e2bfdafeffe597ce44ea51e8b0becd3808856df54cf5e164a502a4d866" } } ], "extra": [ 1, 84, 77, 168, 116, 37, 72, 3, 230, 124, 35, 55, 148, 237, 117, 160, 18, 19, 165, 180, 183, 221, 181, 208, 249, 194, 193, 51, 155, 242, 175, 124, 59, 2, 17, 0, 0, 0, 8, 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