Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea74e67b5d889f3f9dbc0b6e6f72f040f716fa907625f90d81a119b87c13b4dd

Tx prefix hash: 13c06c78c572d3f72a2347af604c49bbb2e713016ecfa460a9193eb2251d1d8b
Tx public key: 9772ece92f94c525fa82c49bfef34ca327f720437eb8aef9ab3a961022d2f151
Timestamp: 1701597098 Timestamp [UCT]: 2023-12-03 09:51:38 Age [y:d:h:m:s]: 01:124:08:49:05
Block: 904986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350038 RingCT/type: yes/0
Extra: 019772ece92f94c525fa82c49bfef34ca327f720437eb8aef9ab3a961022d2f15102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.615751786000 dcy

stealth address amount amount idx
00: da7e878d29b4e5646ff9b3e9dfeb49158fd382fc32c8af04ed493502b9b3dfe7 0.615751786000 1361803 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": 904996, "vin": [ { "gen": { "height": 904986 } } ], "vout": [ { "amount": 615751786, "target": { "key": "da7e878d29b4e5646ff9b3e9dfeb49158fd382fc32c8af04ed493502b9b3dfe7" } } ], "extra": [ 1, 151, 114, 236, 233, 47, 148, 197, 37, 250, 130, 196, 155, 254, 243, 76, 163, 39, 247, 32, 67, 126, 184, 174, 249, 171, 58, 150, 16, 34, 210, 241, 81, 2, 17, 0, 0, 0, 2, 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