Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41eb119317e69fe7e4b5c4b9ca7199b353fe809dc9b428f768c5eec020b520b6

Tx prefix hash: 13a3bdd30f5bd21373610f7b82c0547f4d4a0bbb54d80727985f7e7427bcaf6f
Tx public key: fcff180a8d6782ae8a506ac98b7bc6c2e283bf88eae6cba0b50bf74f72f51021
Timestamp: 1704202275 Timestamp [UCT]: 2024-01-02 13:31:15 Age [y:d:h:m:s]: 01:334:18:48:12
Block: 926572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498143 RingCT/type: yes/0
Extra: 01fcff180a8d6782ae8a506ac98b7bc6c2e283bf88eae6cba0b50bf74f72f5102102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b68846ef95d5a9d346769d91ac3912aa9258182e144c00d4aeae29f7b016a4 0.600000000000 1384366 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": 926582, "vin": [ { "gen": { "height": 926572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b68846ef95d5a9d346769d91ac3912aa9258182e144c00d4aeae29f7b016a4" } } ], "extra": [ 1, 252, 255, 24, 10, 141, 103, 130, 174, 138, 80, 106, 201, 139, 123, 198, 194, 226, 131, 191, 136, 234, 230, 203, 160, 181, 11, 247, 79, 114, 245, 16, 33, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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