Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b78690afc81d89c22d9affa431c46fae9532d2be7ec3453044d2a24fbb86e9

Tx prefix hash: 41b30c59f3146a03ef3aadd222cd6eef0d42442e31eddb2f1d3ee9ed26835e7a
Tx public key: 859da55f5960640177a06971c778d1fb8b72b88f7f219885c2038b457d830a42
Timestamp: 1727657837 Timestamp [UCT]: 2024-09-30 00:57:17 Age [y:d:h:m:s]: 00:104:04:42:00
Block: 1121043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74491 RingCT/type: yes/0
Extra: 01859da55f5960640177a06971c778d1fb8b72b88f7f219885c2038b457d830a4202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c7cf0ae4b26acb075b9ae5ca229e82c6b36d61bbf778f0c612fba5548607e7 0.600000000000 1603174 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": 1121053, "vin": [ { "gen": { "height": 1121043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c7cf0ae4b26acb075b9ae5ca229e82c6b36d61bbf778f0c612fba5548607e7" } } ], "extra": [ 1, 133, 157, 165, 95, 89, 96, 100, 1, 119, 160, 105, 113, 199, 120, 209, 251, 139, 114, 184, 143, 127, 33, 152, 133, 194, 3, 139, 69, 125, 131, 10, 66, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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