Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f067e3ae5118b55fae7d6e1d79f861a1fdd6c723d49054cce7f846f6a3a1312

Tx prefix hash: 88da524e68bf256764cefe408d9243901585333b1b00a5de3063dcce312cb5d4
Tx public key: 09df9a04414494e8ec2e4f08fc5796fc1bec7054d8e1ce75ae5db1e775ea0ad5
Timestamp: 1722449213 Timestamp [UCT]: 2024-07-31 18:06:53 Age [y:d:h:m:s]: 00:267:00:05:16
Block: 1077854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190747 RingCT/type: yes/0
Extra: 0109df9a04414494e8ec2e4f08fc5796fc1bec7054d8e1ce75ae5db1e775ea0ad502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a557c8ffc4e8a3307e83d1c83272482935170126216b9a60cfd16ddeff62cc43 0.600000000000 1550409 of 15

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": 1077864, "vin": [ { "gen": { "height": 1077854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a557c8ffc4e8a3307e83d1c83272482935170126216b9a60cfd16ddeff62cc43" } } ], "extra": [ 1, 9, 223, 154, 4, 65, 68, 148, 232, 236, 46, 79, 8, 252, 87, 150, 252, 27, 236, 112, 84, 216, 225, 206, 117, 174, 93, 177, 231, 117, 234, 10, 213, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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