Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21cea839ecea1484dd6e363ce0cdd28ea36d346304561214edc3bd904b978e76

Tx prefix hash: 664384ec48a5f6c13a2d2ef9f75c4936de11050d06a7a74246061a39d759b1e6
Tx public key: ce81c311b30149767a6477ccf814d7aa2b7415543ff4e363dc7ee496eaa693bf
Timestamp: 1712358022 Timestamp [UCT]: 2024-04-05 23:00:22 Age [y:d:h:m:s]: 01:063:05:29:52
Block: 994166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306222 RingCT/type: yes/0
Extra: 01ce81c311b30149767a6477ccf814d7aa2b7415543ff4e363dc7ee496eaa693bf02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af8770b22a5773cfc1e2ef027bca6e7c5f3013ad6201064d6cd7df41502ea1f 0.600000000000 1454568 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": 994176, "vin": [ { "gen": { "height": 994166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af8770b22a5773cfc1e2ef027bca6e7c5f3013ad6201064d6cd7df41502ea1f" } } ], "extra": [ 1, 206, 129, 195, 17, 179, 1, 73, 118, 122, 100, 119, 204, 248, 20, 215, 170, 43, 116, 21, 84, 63, 244, 227, 99, 220, 126, 228, 150, 234, 166, 147, 191, 2, 17, 0, 0, 0, 2, 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