Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c89e34513ac5a1a0a8a30ed01942958264dc37ae39e9f08e9c3747c64ed287f

Tx prefix hash: 839a9dab07d27c774198bb65499956d0c6ea032239f8a3a77069edf2bad68838
Tx public key: 478c2ab955c726b471cba5d44b24e95c14133bdd635e8e2e2dd876b9a16cf854
Timestamp: 1725113198 Timestamp [UCT]: 2024-08-31 14:06:38 Age [y:d:h:m:s]: 00:213:11:31:53
Block: 1099944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152414 RingCT/type: yes/0
Extra: 01478c2ab955c726b471cba5d44b24e95c14133bdd635e8e2e2dd876b9a16cf85402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b414feda00e43222c86c87aa31016bea358cbc6ccf31404347fd7a2da3f61670 0.600000000000 1575913 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": 1099954, "vin": [ { "gen": { "height": 1099944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b414feda00e43222c86c87aa31016bea358cbc6ccf31404347fd7a2da3f61670" } } ], "extra": [ 1, 71, 140, 42, 185, 85, 199, 38, 180, 113, 203, 165, 212, 75, 36, 233, 92, 20, 19, 59, 221, 99, 94, 142, 46, 45, 216, 118, 185, 161, 108, 248, 84, 2, 17, 0, 0, 0, 9, 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