Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed7013e1114a08eee05eab007618e7774eeae0937194f51d56173d9f64b11680

Tx prefix hash: a43489691537f0726568060ef3d51df66bbc11d33dff6eb8ae63cc9f4d18a325
Tx public key: b5b9557c5bafb7f748e9e636ea956147e42350e5f8903f376140660583ee7eed
Timestamp: 1583811177 Timestamp [UCT]: 2020-03-10 03:32:57 Age [y:d:h:m:s]: 04:251:02:52:37
Block: 79578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074474 RingCT/type: yes/0
Extra: 01b5b9557c5bafb7f748e9e636ea956147e42350e5f8903f376140660583ee7eed0211000000164ac5aa02000000000000000000

1 output(s) for total of 334.445873737000 dcy

stealth address amount amount idx
00: 04379e2da63ba396303ac3b6e7bec94dcc29eedf1fd6e66987b071af1eba0240 334.445873737000 145618 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": 79588, "vin": [ { "gen": { "height": 79578 } } ], "vout": [ { "amount": 334445873737, "target": { "key": "04379e2da63ba396303ac3b6e7bec94dcc29eedf1fd6e66987b071af1eba0240" } } ], "extra": [ 1, 181, 185, 85, 124, 91, 175, 183, 247, 72, 233, 230, 54, 234, 149, 97, 71, 228, 35, 80, 229, 248, 144, 63, 55, 97, 64, 102, 5, 131, 238, 126, 237, 2, 17, 0, 0, 0, 22, 74, 197, 170, 2, 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