Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb231f754865ce37902d39e9933d8a561e43608e75a780b2e45c712e916ce64c

Tx prefix hash: 304200732b87d99b82ee7e1f0768c93861ae909298ddf8b7cbff38530e76cacf
Tx public key: a444e5186f017da75e3c7c27b5d6bc9c25b1e08f1f599fa98d5d21859234117e
Timestamp: 1704962339 Timestamp [UCT]: 2024-01-11 08:38:59 Age [y:d:h:m:s]: 02:022:05:53:00
Block: 932869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535516 RingCT/type: yes/0
Extra: 01a444e5186f017da75e3c7c27b5d6bc9c25b1e08f1f599fa98d5d21859234117e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0aaac349f2ea176fea42a3dba92ab89a2ee81f366deddbaf6777467aea8c526 0.600000000000 1390809 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": 932879, "vin": [ { "gen": { "height": 932869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0aaac349f2ea176fea42a3dba92ab89a2ee81f366deddbaf6777467aea8c526" } } ], "extra": [ 1, 164, 68, 229, 24, 111, 1, 125, 167, 94, 60, 124, 39, 181, 214, 188, 156, 37, 177, 224, 143, 31, 89, 159, 169, 141, 93, 33, 133, 146, 52, 17, 126, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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