Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43193dfa27950031ad9743e2508f0623992777d0f6b2d25c8e73b588443056a

Tx prefix hash: dbf42ef3d1d40e4ef9f2da3c4d02ad94c8e79afc944ded3d3991a22d5d0148ed
Tx public key: 2f87e125ec0d71869841e944d13c82cbfbeaa060ea5815e664d2164ab18413ff
Timestamp: 1636679676 Timestamp [UCT]: 2021-11-12 01:14:36 Age [y:d:h:m:s]: 03:046:13:38:29
Block: 372463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811906 RingCT/type: yes/0
Extra: 012f87e125ec0d71869841e944d13c82cbfbeaa060ea5815e664d2164ab18413ff021100000009745f00f8000000000000000000

1 output(s) for total of 35.800028823000 dcy

stealth address amount amount idx
00: b194d29d392cb855bd9e6d577ccc3bf0bb63896d376ea297cfb096b10a5ae1aa 35.800028823000 754499 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": 372473, "vin": [ { "gen": { "height": 372463 } } ], "vout": [ { "amount": 35800028823, "target": { "key": "b194d29d392cb855bd9e6d577ccc3bf0bb63896d376ea297cfb096b10a5ae1aa" } } ], "extra": [ 1, 47, 135, 225, 37, 236, 13, 113, 134, 152, 65, 233, 68, 209, 60, 130, 203, 251, 234, 160, 96, 234, 88, 21, 230, 100, 210, 22, 74, 177, 132, 19, 255, 2, 17, 0, 0, 0, 9, 116, 95, 0, 248, 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