Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca9aacdec3bfb4c91572c2df566fef19f5ede50e4e00337ad5cfc62495d52d9

Tx prefix hash: cf132e0178a1c2d8864afd2e80e6f84489c57152c3bc8f3b035d9ac4bd7c3b91
Tx public key: b0ad2e7c80caee24fc4c721fbc41ff4a335a3b61520e97048b60541a190f3a13
Timestamp: 1713166351 Timestamp [UCT]: 2024-04-15 07:32:31 Age [y:d:h:m:s]: 01:199:06:03:03
Block: 1000893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401067 RingCT/type: yes/0
Extra: 01b0ad2e7c80caee24fc4c721fbc41ff4a335a3b61520e97048b60541a190f3a1302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28260b62153ac0277a7cb0592e91734b10ec010b73b8ae660d20f304f7c0563f 0.600000000000 1461393 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": 1000903, "vin": [ { "gen": { "height": 1000893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28260b62153ac0277a7cb0592e91734b10ec010b73b8ae660d20f304f7c0563f" } } ], "extra": [ 1, 176, 173, 46, 124, 128, 202, 238, 36, 252, 76, 114, 31, 188, 65, 255, 74, 51, 90, 59, 97, 82, 14, 151, 4, 139, 96, 84, 26, 25, 15, 58, 19, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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