Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 500c6ba8f86d89228ae1ce69e84a95cc7bad8614ec8861136348c4cea78441fb

Tx prefix hash: 42814056a780c7b0a0a214577d7993a39f5efc7ce8005ceb2f331b1f491c6ae1
Tx public key: 36e5c1f6b370725d3e351efc19ec3c43455d4f7fcbe82111469830a86fe7c1a3
Timestamp: 1734232286 Timestamp [UCT]: 2024-12-15 03:11:26 Age [y:d:h:m:s]: 00:108:19:19:53
Block: 1175461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77523 RingCT/type: yes/0
Extra: 0136e5c1f6b370725d3e351efc19ec3c43455d4f7fcbe82111469830a86fe7c1a3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf1f2806ae4f046164cc585273ae79a0bac606a66963f1585cf3f6e6554f630 0.600000000000 1661744 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": 1175471, "vin": [ { "gen": { "height": 1175461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf1f2806ae4f046164cc585273ae79a0bac606a66963f1585cf3f6e6554f630" } } ], "extra": [ 1, 54, 229, 193, 246, 179, 112, 114, 93, 62, 53, 30, 252, 25, 236, 60, 67, 69, 93, 79, 127, 203, 232, 33, 17, 70, 152, 48, 168, 111, 231, 193, 163, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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