Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb04a362ced0a1532cb0aadd7e8599d56f467374ad01f5247108b3ebef544d6

Tx prefix hash: 06b3b4fa32747d5fe872ec2b2286c930899538738f98a1c2abcd4575e0c40a17
Tx public key: 31cde8938a832937405c821a13f0c20a5f92ae5e080b1d29e65b5ae6b4c322c6
Timestamp: 1727831599 Timestamp [UCT]: 2024-10-02 01:13:19 Age [y:d:h:m:s]: 00:112:14:45:04
Block: 1122488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80462 RingCT/type: yes/0
Extra: 0131cde8938a832937405c821a13f0c20a5f92ae5e080b1d29e65b5ae6b4c322c6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7333f3e548f220f87ae2b8a794fea65ee17381f70487f8ac5c731e9e82a1b5b5 0.600000000000 1604935 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": 1122498, "vin": [ { "gen": { "height": 1122488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7333f3e548f220f87ae2b8a794fea65ee17381f70487f8ac5c731e9e82a1b5b5" } } ], "extra": [ 1, 49, 205, 232, 147, 138, 131, 41, 55, 64, 92, 130, 26, 19, 240, 194, 10, 95, 146, 174, 94, 8, 11, 29, 41, 230, 91, 90, 230, 180, 195, 34, 198, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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