Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ccce9c9e8e3ff5d94c12893e0873bc806090aea6ab54e13a90e130605e248e

Tx prefix hash: 118c066abb0c38ae2738ce1a6c336bca5000cee3efd52372564c53c10de2d2b9
Tx public key: b7366b2ebfe1256eca073f5b2a2c8b1cf8daaa1844780d6ea85ab2cc4b764624
Timestamp: 1694737655 Timestamp [UCT]: 2023-09-15 00:27:35 Age [y:d:h:m:s]: 01:034:16:53:15
Block: 848301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286127 RingCT/type: yes/0
Extra: 01b7366b2ebfe1256eca073f5b2a2c8b1cf8daaa1844780d6ea85ab2cc4b764624021100000001faf35c9c000000000000000000

1 output(s) for total of 0.948913662000 dcy

stealth address amount amount idx
00: 0e2ac9e8eb0e5547a4b089d0a37f3018f932f3e808ec1cf65b88aecbf29f54cc 0.948913662000 1301895 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": 848311, "vin": [ { "gen": { "height": 848301 } } ], "vout": [ { "amount": 948913662, "target": { "key": "0e2ac9e8eb0e5547a4b089d0a37f3018f932f3e808ec1cf65b88aecbf29f54cc" } } ], "extra": [ 1, 183, 54, 107, 46, 191, 225, 37, 110, 202, 7, 63, 91, 42, 44, 139, 28, 248, 218, 170, 24, 68, 120, 13, 110, 168, 90, 178, 204, 75, 118, 70, 36, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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