Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1dd0694af43178b5581a0db991aa34ce93a19e85b2fa4c46e7fcb5ecb82931

Tx prefix hash: 440bd26c5a54e140ea0f8b0c963a509bc3c33213eedbfb2edb17a609ae75f80d
Tx public key: e82609934f465b6b143353209b74f450c4c7a497b0ff878a4c9531e5f8dbe29f
Timestamp: 1673266924 Timestamp [UCT]: 2023-01-09 12:22:04 Age [y:d:h:m:s]: 02:106:20:45:33
Block: 670970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598081 RingCT/type: yes/0
Extra: 01e82609934f465b6b143353209b74f450c4c7a497b0ff878a4c9531e5f8dbe29f02110000000352542ceb000000000000000000

1 output(s) for total of 3.671113509000 dcy

stealth address amount amount idx
00: 2be60095874010c9c5a3564337c74e564bb3b7038000f8d294e05a2d516ede95 3.671113509000 1112421 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": 670980, "vin": [ { "gen": { "height": 670970 } } ], "vout": [ { "amount": 3671113509, "target": { "key": "2be60095874010c9c5a3564337c74e564bb3b7038000f8d294e05a2d516ede95" } } ], "extra": [ 1, 232, 38, 9, 147, 79, 70, 91, 107, 20, 51, 83, 32, 155, 116, 244, 80, 196, 199, 164, 151, 176, 255, 135, 138, 76, 149, 49, 229, 248, 219, 226, 159, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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