Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 237a96d00f6c1eac9b9034f7db781c9f382b688ebe5f96bf2c068949574a2e21

Tx prefix hash: 84031b33ed8f831d96e18a228e8a3ac40276749418ec3087480d035ac04758fd
Tx public key: 6f8d157a4ae011f3da68ac73aa093b586d88e3a0fabc55d440c39e2deb0003a6
Timestamp: 1734753572 Timestamp [UCT]: 2024-12-21 03:59:32 Age [y:d:h:m:s]: 00:015:02:34:44
Block: 1179783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10785 RingCT/type: yes/0
Extra: 016f8d157a4ae011f3da68ac73aa093b586d88e3a0fabc55d440c39e2deb0003a60211000000181f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddfbb55465be2399c1c9bb6562931211d937cbcdbb382f8531d673a376d6ff65 0.600000000000 1666182 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": 1179793, "vin": [ { "gen": { "height": 1179783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddfbb55465be2399c1c9bb6562931211d937cbcdbb382f8531d673a376d6ff65" } } ], "extra": [ 1, 111, 141, 21, 122, 74, 224, 17, 243, 218, 104, 172, 115, 170, 9, 59, 88, 109, 136, 227, 160, 250, 188, 85, 212, 64, 195, 158, 45, 235, 0, 3, 166, 2, 17, 0, 0, 0, 24, 31, 10, 83, 235, 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