Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cbaa7d9d3e82dfd058bff9f17f33884038ba6107e79b06529ce8ed8f9232b07

Tx prefix hash: f048f61588d3795da68e118ca291ec21b87d646f67ba1a62a371fd2184a044d4
Tx public key: 39ad8e506e7882539776982f99a2d94d06423abf25caef47e4005aeef3ed340f
Timestamp: 1721521856 Timestamp [UCT]: 2024-07-21 00:30:56 Age [y:d:h:m:s]: 00:244:12:29:15
Block: 1070166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174684 RingCT/type: yes/0
Extra: 0139ad8e506e7882539776982f99a2d94d06423abf25caef47e4005aeef3ed340f0211000000010cce0636000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: f8b98be089f3e7dbcc4143801567664ba5e327d65c0f858cf85dfe8a0a6f6c9e 0.615610000000 1541887 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": 1070176, "vin": [ { "gen": { "height": 1070166 } } ], "vout": [ { "amount": 615610000, "target": { "key": "f8b98be089f3e7dbcc4143801567664ba5e327d65c0f858cf85dfe8a0a6f6c9e" } } ], "extra": [ 1, 57, 173, 142, 80, 110, 120, 130, 83, 151, 118, 152, 47, 153, 162, 217, 77, 6, 66, 58, 191, 37, 202, 239, 71, 228, 0, 90, 238, 243, 237, 52, 15, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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