Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6ac0b54e25cdb0e4222d2d895596c13b54192c1538c427de4140adbc2da2fc

Tx prefix hash: 941e3ecd16f5aa2cc7488919a8f6dac4d9eb6a72158ebabf5017c176d250ba29
Tx public key: cacf5b8983b147d8c537c675744d03d216a20c0d95b6b48ee559928a52a464d1
Timestamp: 1677088038 Timestamp [UCT]: 2023-02-22 17:47:18 Age [y:d:h:m:s]: 02:049:14:21:31
Block: 702676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557042 RingCT/type: yes/0
Extra: 01cacf5b8983b147d8c537c675744d03d216a20c0d95b6b48ee559928a52a464d102110000000474b6d784000000000000000000

1 output(s) for total of 2.882322863000 dcy

stealth address amount amount idx
00: 67788de08dc74ee47d0c1fc926cbf7525b1189a8097e7a67f37cc3816dfa2e84 2.882322863000 1146215 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": 702686, "vin": [ { "gen": { "height": 702676 } } ], "vout": [ { "amount": 2882322863, "target": { "key": "67788de08dc74ee47d0c1fc926cbf7525b1189a8097e7a67f37cc3816dfa2e84" } } ], "extra": [ 1, 202, 207, 91, 137, 131, 177, 71, 216, 197, 55, 198, 117, 116, 77, 3, 210, 22, 162, 12, 13, 149, 182, 180, 142, 229, 89, 146, 138, 82, 164, 100, 209, 2, 17, 0, 0, 0, 4, 116, 182, 215, 132, 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