Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5baf240ec59ece98606208d79f31a29b21e9fadf676fbc3c448cf078e4931f46

Tx prefix hash: 6fbb1bdc6b3407c81c25595ed925a5ffd43e347b199fbffc4d263551f6595686
Tx public key: 9e313a6f92bb0d3cef2e395de065db7cc4e979eb3f242fd3a0ca41183225d33b
Timestamp: 1674953305 Timestamp [UCT]: 2023-01-29 00:48:25 Age [y:d:h:m:s]: 01:296:13:34:31
Block: 684965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472912 RingCT/type: yes/0
Extra: 019e313a6f92bb0d3cef2e395de065db7cc4e979eb3f242fd3a0ca41183225d33b02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.299336016000 dcy

stealth address amount amount idx
00: babeda50ed9a27b9ce1565bd0f11547a5412c3f1882d180db396fbc6f250140d 3.299336016000 1127248 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": 684975, "vin": [ { "gen": { "height": 684965 } } ], "vout": [ { "amount": 3299336016, "target": { "key": "babeda50ed9a27b9ce1565bd0f11547a5412c3f1882d180db396fbc6f250140d" } } ], "extra": [ 1, 158, 49, 58, 111, 146, 187, 13, 60, 239, 46, 57, 93, 224, 101, 219, 124, 196, 233, 121, 235, 63, 36, 47, 211, 160, 202, 65, 24, 50, 37, 211, 59, 2, 17, 0, 0, 0, 1, 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