Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b2563019e0f0f18e3bbbf495c6681965944ab7216a045f3c39e8487bad05b6

Tx prefix hash: 648298b251a917a03e9a5da3258bb817630cab97c1a5e917017ddabf0f27cf10
Tx public key: b41e36e5a47fe93781e4958c5bce36fdba2a57745e4eca384ae87cbad56b9e59
Timestamp: 1699343186 Timestamp [UCT]: 2023-11-07 07:46:26 Age [y:d:h:m:s]: 01:075:01:11:05
Block: 886308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315000 RingCT/type: yes/0
Extra: 01b41e36e5a47fe93781e4958c5bce36fdba2a57745e4eca384ae87cbad56b9e5902110000000975e3f0e9000000000000000000

1 output(s) for total of 0.710057756000 dcy

stealth address amount amount idx
00: a49cdbf793f611e46189d4878e118c1df2d41958818edbb2ef7d17a7fa25a0a1 0.710057756000 1342121 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": 886318, "vin": [ { "gen": { "height": 886308 } } ], "vout": [ { "amount": 710057756, "target": { "key": "a49cdbf793f611e46189d4878e118c1df2d41958818edbb2ef7d17a7fa25a0a1" } } ], "extra": [ 1, 180, 30, 54, 229, 164, 127, 233, 55, 129, 228, 149, 140, 91, 206, 54, 253, 186, 42, 87, 116, 94, 78, 202, 56, 74, 232, 124, 186, 213, 107, 158, 89, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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