Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb3133590bea7863f534522ad7a867b10bf154eb2a2f1a994f33e5c68f6ba86c

Tx prefix hash: a5610995b87d2a2eac4c103632738728bcccc903844d6aed7cf3db685b967712
Tx public key: 8de094dd3d55cdc9f5e91bbb2a8c16e487d2ad1568d7019419786964a3ab7170
Timestamp: 1696927720 Timestamp [UCT]: 2023-10-10 08:48:40 Age [y:d:h:m:s]: 01:212:21:38:06
Block: 866487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413208 RingCT/type: yes/0
Extra: 018de094dd3d55cdc9f5e91bbb2a8c16e487d2ad1568d7019419786964a3ab717002110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.825978809000 dcy

stealth address amount amount idx
00: f93044f75eb3890eecfd4f1a55eb3ff1663ad25fd0df5285e449ed0f9bb36fc7 0.825978809000 1321083 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": 866497, "vin": [ { "gen": { "height": 866487 } } ], "vout": [ { "amount": 825978809, "target": { "key": "f93044f75eb3890eecfd4f1a55eb3ff1663ad25fd0df5285e449ed0f9bb36fc7" } } ], "extra": [ 1, 141, 224, 148, 221, 61, 85, 205, 201, 245, 233, 27, 187, 42, 140, 22, 228, 135, 210, 173, 21, 104, 215, 1, 148, 25, 120, 105, 100, 163, 171, 113, 112, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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