Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4330e8b0bd59319efaee1263f06e1bfef7054465558eacf5e6903ab417c598c1

Tx prefix hash: aa40d5eae23970e6d332ea5b13920f2ab33aadd10ab704f777a74e871315b3ee
Tx public key: 6bb4951a5feee9743984ec8b9a4795d0bf92504129d4306981848dd1a57f3119
Timestamp: 1700941466 Timestamp [UCT]: 2023-11-25 19:44:26 Age [y:d:h:m:s]: 01:190:08:31:54
Block: 899544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397259 RingCT/type: yes/0
Extra: 016bb4951a5feee9743984ec8b9a4795d0bf92504129d4306981848dd1a57f311902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.641855539000 dcy

stealth address amount amount idx
00: 8f3191f9475a5be37c2ff6b13c98a94cfb8d0cafd22c8b828683a466d5373fd3 0.641855539000 1356001 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": 899554, "vin": [ { "gen": { "height": 899544 } } ], "vout": [ { "amount": 641855539, "target": { "key": "8f3191f9475a5be37c2ff6b13c98a94cfb8d0cafd22c8b828683a466d5373fd3" } } ], "extra": [ 1, 107, 180, 149, 26, 95, 238, 233, 116, 57, 132, 236, 139, 154, 71, 149, 208, 191, 146, 80, 65, 41, 212, 48, 105, 129, 132, 141, 209, 165, 127, 49, 25, 2, 17, 0, 0, 0, 2, 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