Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a4ec2133ab8f739603cae4f8f2ff9c2db67aa0c0de146299bacd310bfe262b

Tx prefix hash: 017036ee05e345d51f625082debaedaa6aa073231bc43c3bed3155c3bb717e20
Tx public key: bdc79fd0f4e578f2c1bcb2e59f21e2b9223139caef47205f42e17a299e597f3a
Timestamp: 1577559732 Timestamp [UCT]: 2019-12-28 19:02:12 Age [y:d:h:m:s]: 04:313:10:31:26
Block: 33739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113138 RingCT/type: yes/0
Extra: 01bdc79fd0f4e578f2c1bcb2e59f21e2b9223139caef47205f42e17a299e597f3a0211000000038a2ee0d9000000000000000000

1 output(s) for total of 474.470858946000 dcy

stealth address amount amount idx
00: a3208c8da17c5b7bafd1fd4b3b50a6058d0ee3c460f9137a716769db8e7456e8 474.470858946000 56592 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": 33749, "vin": [ { "gen": { "height": 33739 } } ], "vout": [ { "amount": 474470858946, "target": { "key": "a3208c8da17c5b7bafd1fd4b3b50a6058d0ee3c460f9137a716769db8e7456e8" } } ], "extra": [ 1, 189, 199, 159, 208, 244, 229, 120, 242, 193, 188, 178, 229, 159, 33, 226, 185, 34, 49, 57, 202, 239, 71, 32, 95, 66, 225, 122, 41, 158, 89, 127, 58, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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