Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a13781302b79b2c947fd3b6ed4774bff3d38aea7d8800115c4e59f771caaf4a8

Tx prefix hash: f32ce0838938e2d6adef7c05d143ab4b828e1c50188eaaa2d75a4f7f93ff9336
Tx public key: 38d7a53220079b0566ce368a5bafc4108b36a01302f872c145b504e649adff64
Timestamp: 1681473031 Timestamp [UCT]: 2023-04-14 11:50:31 Age [y:d:h:m:s]: 01:271:07:56:57
Block: 738387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455423 RingCT/type: yes/0
Extra: 0138d7a53220079b0566ce368a5bafc4108b36a01302f872c145b504e649adff64021100000007b3164c24000000000000000000

1 output(s) for total of 2.194914311000 dcy

stealth address amount amount idx
00: 92e37b3a1881a2fe4d426fd6daced2157001e0c577bdf08e7a5e7ef8f8e966a8 2.194914311000 1185068 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": 738397, "vin": [ { "gen": { "height": 738387 } } ], "vout": [ { "amount": 2194914311, "target": { "key": "92e37b3a1881a2fe4d426fd6daced2157001e0c577bdf08e7a5e7ef8f8e966a8" } } ], "extra": [ 1, 56, 215, 165, 50, 32, 7, 155, 5, 102, 206, 54, 138, 91, 175, 196, 16, 139, 54, 160, 19, 2, 248, 114, 193, 69, 181, 4, 230, 73, 173, 255, 100, 2, 17, 0, 0, 0, 7, 179, 22, 76, 36, 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