Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 984e5bcc4e8db653a2acdaaca0bb0f3d619eacfdccfd6b99b7d243e3cb7a5951

Tx prefix hash: 596df23b0a761629342d68b26f96aec5414f508c688cbc2fe142f01991d6a251
Tx public key: a54c631909635a4ef41dd46b2f90a140cd4438f1876bff22b7e2bbdaa20ef311
Timestamp: 1717968285 Timestamp [UCT]: 2024-06-09 21:24:45 Age [y:d:h:m:s]: 00:282:12:33:06
Block: 1040706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201923 RingCT/type: yes/0
Extra: 01a54c631909635a4ef41dd46b2f90a140cd4438f1876bff22b7e2bbdaa20ef3110211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 407da52367ed3f535f39323d24f4a6748423ab7eb0aa7809d063010b85e5ac18 0.600000000000 1509365 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": 1040716, "vin": [ { "gen": { "height": 1040706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "407da52367ed3f535f39323d24f4a6748423ab7eb0aa7809d063010b85e5ac18" } } ], "extra": [ 1, 165, 76, 99, 25, 9, 99, 90, 78, 244, 29, 212, 107, 47, 144, 161, 64, 205, 68, 56, 241, 135, 107, 255, 34, 183, 226, 187, 218, 162, 14, 243, 17, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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