Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7d85cfdef2d6f30a035a2ec1337d0f18fe04f8b45572bbc1c4b954f9c3e683

Tx prefix hash: 231366d72f913f229629b4c1285205f33c5579d5222bfd28457f3a77970fce70
Tx public key: bbb9607d443ad4d945864117cbabf08644ba8a37f82177871881cb53f1df9f2c
Timestamp: 1730586038 Timestamp [UCT]: 2024-11-02 22:20:38 Age [y:d:h:m:s]: 00:156:19:26:57
Block: 1145228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111906 RingCT/type: yes/0
Extra: 01bbb9607d443ad4d945864117cbabf08644ba8a37f82177871881cb53f1df9f2c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1f5ac009acf2e3067ebc5359778558d293b79dbf715771ff05a856893d0c3c0 0.600000000000 1629629 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": 1145238, "vin": [ { "gen": { "height": 1145228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1f5ac009acf2e3067ebc5359778558d293b79dbf715771ff05a856893d0c3c0" } } ], "extra": [ 1, 187, 185, 96, 125, 68, 58, 212, 217, 69, 134, 65, 23, 203, 171, 240, 134, 68, 186, 138, 55, 248, 33, 119, 135, 24, 129, 203, 83, 241, 223, 159, 44, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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