Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe36409f62b038cecc0ebb8dbd96b4e7bc5e38fae4983c4f80417e8a126bb41

Tx prefix hash: 5dcf5a5194ffd79c28683eb4a0ed59b7cafc4211c829389392327eec83743e9a
Tx public key: eca64326a4c4b468b4305e0b8003942cd395ee22be7d4b749fddf0cbd06d0f7e
Timestamp: 1700773521 Timestamp [UCT]: 2023-11-23 21:05:21 Age [y:d:h:m:s]: 01:057:19:50:32
Block: 898150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302689 RingCT/type: yes/0
Extra: 01eca64326a4c4b468b4305e0b8003942cd395ee22be7d4b749fddf0cbd06d0f7e021100000004679a8a81000000000000000000

1 output(s) for total of 0.648718370000 dcy

stealth address amount amount idx
00: 48f87916363e4462bf7e23615f4e612030e70eae3a0eca09e91abe1181ebe875 0.648718370000 1354555 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": 898160, "vin": [ { "gen": { "height": 898150 } } ], "vout": [ { "amount": 648718370, "target": { "key": "48f87916363e4462bf7e23615f4e612030e70eae3a0eca09e91abe1181ebe875" } } ], "extra": [ 1, 236, 166, 67, 38, 164, 196, 180, 104, 180, 48, 94, 11, 128, 3, 148, 44, 211, 149, 238, 34, 190, 125, 75, 116, 159, 221, 240, 203, 208, 109, 15, 126, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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