Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3750f3ab975ae20f5fcaa02853a0dcd49254f18f6e8863137890a1b728adab9a

Tx prefix hash: 81a3da053ba9ee48a0ab76e38f79fab12941821cab573e70a3b4de14417be00c
Tx public key: c87910722b8433eade86062b25e0f5599a0aa8fdf1fa85cd4e14051bc6e74227
Timestamp: 1736626997 Timestamp [UCT]: 2025-01-11 20:23:17 Age [y:d:h:m:s]: 00:083:20:29:11
Block: 1195255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59713 RingCT/type: yes/0
Extra: 01c87910722b8433eade86062b25e0f5599a0aa8fdf1fa85cd4e14051bc6e742270211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e602fa94c959e7a26be0a38d2ee1eaecb0fd89421836359f5df02502b2c59644 0.600000000000 1681844 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": 1195265, "vin": [ { "gen": { "height": 1195255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e602fa94c959e7a26be0a38d2ee1eaecb0fd89421836359f5df02502b2c59644" } } ], "extra": [ 1, 200, 121, 16, 114, 43, 132, 51, 234, 222, 134, 6, 43, 37, 224, 245, 89, 154, 10, 168, 253, 241, 250, 133, 205, 78, 20, 5, 27, 198, 231, 66, 39, 2, 17, 0, 0, 0, 5, 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