Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 875deae44119ab610158663d99e2d8ab318e5591d4bf449875d5d8e737cedd46

Tx prefix hash: 8eace1af2400904b825da2c8024f58b05ea89ef36ab4b290b5fc93e7e0adb87b
Tx public key: 22e26efe4bb7559390436534dcb8d3519a354dc7a1c627c2bff626e6fe411604
Timestamp: 1705153012 Timestamp [UCT]: 2024-01-13 13:36:52 Age [y:d:h:m:s]: 01:312:08:51:07
Block: 934449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482081 RingCT/type: yes/0
Extra: 0122e26efe4bb7559390436534dcb8d3519a354dc7a1c627c2bff626e6fe411604021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f67890288bd4958bb9676ab3dc9bc0787b98a2f68299db5523d9063e2e29b7 0.600000000000 1392457 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": 934459, "vin": [ { "gen": { "height": 934449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f67890288bd4958bb9676ab3dc9bc0787b98a2f68299db5523d9063e2e29b7" } } ], "extra": [ 1, 34, 226, 110, 254, 75, 183, 85, 147, 144, 67, 101, 52, 220, 184, 211, 81, 154, 53, 77, 199, 161, 198, 39, 194, 191, 246, 38, 230, 254, 65, 22, 4, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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