Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb9a095e0d9adcbc51cdfd342f0544ab2598b40a2e86c8098eaa5e3460e692b

Tx prefix hash: 5f04638cdf0f54a333ce0e3ecc46919ae1dde2118a91641471211440f957ea43
Tx public key: 0fd66f1ae41f5a8e0dcfedfd3544bcf0e73e98d2509cfdcdf751f2853e57db99
Timestamp: 1717716651 Timestamp [UCT]: 2024-06-06 23:30:51 Age [y:d:h:m:s]: 00:331:12:47:56
Block: 1038630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236947 RingCT/type: yes/0
Extra: 010fd66f1ae41f5a8e0dcfedfd3544bcf0e73e98d2509cfdcdf751f2853e57db99021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a51ee4f9351f5a5b9bf2721c8bd6023d0e5dfe2487565f13e570162b157109 0.600000000000 1507191 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": 1038640, "vin": [ { "gen": { "height": 1038630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a51ee4f9351f5a5b9bf2721c8bd6023d0e5dfe2487565f13e570162b157109" } } ], "extra": [ 1, 15, 214, 111, 26, 228, 31, 90, 142, 13, 207, 237, 253, 53, 68, 188, 240, 231, 62, 152, 210, 80, 156, 253, 205, 247, 81, 242, 133, 62, 87, 219, 153, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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