Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044ed0c99b7b69ad96c8888b5e1600bd7487bd188f068b435d13810a5345ee57

Tx prefix hash: 3db954c36d37e4699d5dcb8df2108b966fbd60d9f0dcf3d0d5234e4cd0cdfae7
Tx public key: 42adb59a9c7ba0c401e15e5a2888a90ace0b7205e2844444c50365eab1a03f2e
Timestamp: 1716105611 Timestamp [UCT]: 2024-05-19 08:00:11 Age [y:d:h:m:s]: 00:196:02:10:33
Block: 1025276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140361 RingCT/type: yes/0
Extra: 0142adb59a9c7ba0c401e15e5a2888a90ace0b7205e2844444c50365eab1a03f2e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c28641dcb60a34a759d064ddd6456af71d46b7350d4431578577f29a6826ecc 0.600000000000 1491663 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": 1025286, "vin": [ { "gen": { "height": 1025276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c28641dcb60a34a759d064ddd6456af71d46b7350d4431578577f29a6826ecc" } } ], "extra": [ 1, 66, 173, 181, 154, 156, 123, 160, 196, 1, 225, 94, 90, 40, 136, 169, 10, 206, 11, 114, 5, 226, 132, 68, 68, 197, 3, 101, 234, 177, 160, 63, 46, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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