Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377e890a586c9f0d1da972ec0604a8ef50daa0c6a3d35901eadea43adec4d659

Tx prefix hash: 9d389900d15cd12fb1a19a48dd6b7f849df740c3a818b65951e2ae3ebd19894f
Tx public key: feaccbdb97f38fe998d6ca86dbe774acb033020ed5d624f9ec8623e58a9a5bfa
Timestamp: 1682464260 Timestamp [UCT]: 2023-04-25 23:11:00 Age [y:d:h:m:s]: 01:358:04:23:15
Block: 746612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517258 RingCT/type: yes/0
Extra: 01feaccbdb97f38fe998d6ca86dbe774acb033020ed5d624f9ec8623e58a9a5bfa02110000000233af99f4000000000000000000

1 output(s) for total of 2.061411615000 dcy

stealth address amount amount idx
00: 295437fe975c8913f234ec85cc98c36b8c59db11adc95196d4ef1e046b20a1cc 2.061411615000 1194191 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": 746622, "vin": [ { "gen": { "height": 746612 } } ], "vout": [ { "amount": 2061411615, "target": { "key": "295437fe975c8913f234ec85cc98c36b8c59db11adc95196d4ef1e046b20a1cc" } } ], "extra": [ 1, 254, 172, 203, 219, 151, 243, 143, 233, 152, 214, 202, 134, 219, 231, 116, 172, 176, 51, 2, 14, 213, 214, 36, 249, 236, 134, 35, 229, 138, 154, 91, 250, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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