Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0db52ef6927e387a51e0e1435b6094dbb00a1d4af56e785d72df4723d34874b0

Tx prefix hash: 2aa41022b3c692a0894432920ffce3007d96e5371e8114ae24b05d22c6a2e779
Tx public key: 0eba28ff4553518fc0cdbd96ed71bb93e9a1cd6cc14c698cb004ad78a19d828d
Timestamp: 1581333228 Timestamp [UCT]: 2020-02-10 11:13:48 Age [y:d:h:m:s]: 04:221:10:20:11
Block: 61834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050507 RingCT/type: yes/0
Extra: 010eba28ff4553518fc0cdbd96ed71bb93e9a1cd6cc14c698cb004ad78a19d828d021100000001c71d3ff9000000000000000000

1 output(s) for total of 383.071977284000 dcy

stealth address amount amount idx
00: 3cb52f8ec97088b54037915584a1e5cda914f18be340360a7af698d8de50c9ed 383.071977284000 114054 of 0

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": 61844, "vin": [ { "gen": { "height": 61834 } } ], "vout": [ { "amount": 383071977284, "target": { "key": "3cb52f8ec97088b54037915584a1e5cda914f18be340360a7af698d8de50c9ed" } } ], "extra": [ 1, 14, 186, 40, 255, 69, 83, 81, 143, 192, 205, 189, 150, 237, 113, 187, 147, 233, 161, 205, 108, 193, 76, 105, 140, 176, 4, 173, 120, 161, 157, 130, 141, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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