Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2db54d8f89b77d98e51cf41138ab1a17051ef591876ce61acf541caed39286c

Tx prefix hash: ac7814f90be65e64692cc47818efdfd2acf1f7c7f71b362a79b04a66f100e45f
Tx public key: 53530b4a313b9ea0ef079b5f2a49fb1c66983ac044df1393ac023794811265a8
Timestamp: 1703651440 Timestamp [UCT]: 2023-12-27 04:30:40 Age [y:d:h:m:s]: 01:327:22:25:23
Block: 922016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493221 RingCT/type: yes/0
Extra: 0153530b4a313b9ea0ef079b5f2a49fb1c66983ac044df1393ac023794811265a80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 744507f93df1dffa1c937ca43e2d17e61963d5aacefdc15cfc41b8b6b0ba6b07 0.600000000000 1379710 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": 922026, "vin": [ { "gen": { "height": 922016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "744507f93df1dffa1c937ca43e2d17e61963d5aacefdc15cfc41b8b6b0ba6b07" } } ], "extra": [ 1, 83, 83, 11, 74, 49, 59, 158, 160, 239, 7, 155, 95, 42, 73, 251, 28, 102, 152, 58, 192, 68, 223, 19, 147, 172, 2, 55, 148, 129, 18, 101, 168, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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