Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e7197be36ac7f1dfb71b0fcf45f619b703d57e68bae6c22ecee8dadce955398

Tx prefix hash: 1e9a01312a109a9329e885131195aa65ff6ef9c7381136683bf240c9b9350fb1
Tx public key: 0c16af48fed22911dc84ebab303be82141872c01a3c49a3aa7a2f2dc7d86f5dc
Timestamp: 1641068251 Timestamp [UCT]: 2022-01-01 20:17:31 Age [y:d:h:m:s]: 03:072:02:19:12
Block: 408387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830321 RingCT/type: yes/0
Extra: 010c16af48fed22911dc84ebab303be82141872c01a3c49a3aa7a2f2dc7d86f5dc02110000001cedb0d4a3000000000000000000

1 output(s) for total of 27.217277334000 dcy

stealth address amount amount idx
00: 14c9a4ee5b8637ff80d56e89c0a07445070b8154306dd1d5a2d000d37e0a39cf 27.217277334000 810406 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": 408397, "vin": [ { "gen": { "height": 408387 } } ], "vout": [ { "amount": 27217277334, "target": { "key": "14c9a4ee5b8637ff80d56e89c0a07445070b8154306dd1d5a2d000d37e0a39cf" } } ], "extra": [ 1, 12, 22, 175, 72, 254, 210, 41, 17, 220, 132, 235, 171, 48, 59, 232, 33, 65, 135, 44, 1, 163, 196, 154, 58, 167, 162, 242, 220, 125, 134, 245, 220, 2, 17, 0, 0, 0, 28, 237, 176, 212, 163, 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