Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8c7400aed118ddf4f64331adfedca8200d5178d9eea3d539153e8180d24760

Tx prefix hash: 589a1c8384bdd127c0d48cc941264fe4ceca015d527af4c4bc5e9a3be37d339e
Tx public key: abaf3c1ee0421a1aebf60282c03a7bef4e62ce0e2849b93a9ae75aa677a143dd
Timestamp: 1711420048 Timestamp [UCT]: 2024-03-26 02:27:28 Age [y:d:h:m:s]: 00:244:01:16:58
Block: 986452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174685 RingCT/type: yes/0
Extra: 01abaf3c1ee0421a1aebf60282c03a7bef4e62ce0e2849b93a9ae75aa677a143dd02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c08122d2996a38ccfb368357663ed7b7478c5ee34bf933d3cde3e55da1e66dc7 0.600000000000 1446681 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": 986462, "vin": [ { "gen": { "height": 986452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c08122d2996a38ccfb368357663ed7b7478c5ee34bf933d3cde3e55da1e66dc7" } } ], "extra": [ 1, 171, 175, 60, 30, 224, 66, 26, 26, 235, 246, 2, 130, 192, 58, 123, 239, 78, 98, 206, 14, 40, 73, 185, 58, 154, 231, 90, 166, 119, 161, 67, 221, 2, 17, 0, 0, 0, 4, 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