Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3a17bf09a2cfe88026101f35a1e4cc60c39bf1f57bd078d4a62c2040b1fb5d7

Tx prefix hash: c5fdf0ccbac052112b9eb9a6129152fa1db8f8fba7f25e2cbf47e23e64b61ea1
Tx public key: 8be408bace366deac17933c9dc1785fd20d73d6799d8d4651c3ff1e037849756
Timestamp: 1578832730 Timestamp [UCT]: 2020-01-12 12:38:50 Age [y:d:h:m:s]: 04:356:07:18:49
Block: 43954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144136 RingCT/type: yes/0
Extra: 018be408bace366deac17933c9dc1785fd20d73d6799d8d4651c3ff1e037849756021100000008dcee4b4d000000000000000000

1 output(s) for total of 438.904955394000 dcy

stealth address amount amount idx
00: a36170cbb2ef6ae398b22cd817099bfcd0be0c6e7dc699dc8eb6c52dc26f2ae6 438.904955394000 79801 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": 43964, "vin": [ { "gen": { "height": 43954 } } ], "vout": [ { "amount": 438904955394, "target": { "key": "a36170cbb2ef6ae398b22cd817099bfcd0be0c6e7dc699dc8eb6c52dc26f2ae6" } } ], "extra": [ 1, 139, 228, 8, 186, 206, 54, 109, 234, 193, 121, 51, 201, 220, 23, 133, 253, 32, 215, 61, 103, 153, 216, 212, 101, 28, 63, 241, 224, 55, 132, 151, 86, 2, 17, 0, 0, 0, 8, 220, 238, 75, 77, 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