Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda0d97453f4f227c4b226bd8159c61eeacd7265ee0ebf428bde32c3539a6f85

Tx prefix hash: f1ff957d982efd24dedd38f32d6725a018cdb1d4b95ed43de87127ce1a010640
Tx public key: a61b3d8e5d69a9bcc704bb5dde83fddfcec932af14161710d808ac7337047d72
Timestamp: 1729561647 Timestamp [UCT]: 2024-10-22 01:47:27 Age [y:d:h:m:s]: 00:091:08:19:00
Block: 1136786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65277 RingCT/type: yes/0
Extra: 01a61b3d8e5d69a9bcc704bb5dde83fddfcec932af14161710d808ac7337047d72021100000002007f978a000000000000000000

1 output(s) for total of 0.600100000000 dcy

stealth address amount amount idx
00: 0f3a570b1552809ff0a2cb60d9b2a76a8bb48af4cb1774dcd1ce64f99e3d70ff 0.600100000000 1620157 of 0

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": 1136796, "vin": [ { "gen": { "height": 1136786 } } ], "vout": [ { "amount": 600100000, "target": { "key": "0f3a570b1552809ff0a2cb60d9b2a76a8bb48af4cb1774dcd1ce64f99e3d70ff" } } ], "extra": [ 1, 166, 27, 61, 142, 93, 105, 169, 188, 199, 4, 187, 93, 222, 131, 253, 223, 206, 201, 50, 175, 20, 22, 23, 16, 216, 8, 172, 115, 55, 4, 125, 114, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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