Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a339ce6d2efc289ac2588214d27a51b0c9e2a1f1aef2bcf15d7bbd0ec343fc3c

Tx prefix hash: 71712fc39839ecc05f7aaf4d007daee3b47bf120772724d14d04792f63957d57
Tx public key: 77469ba2790b083b2c81be7280537057bd9ca1a2c0432df3c62132a71395fb5e
Timestamp: 1638453293 Timestamp [UCT]: 2021-12-02 13:54:53 Age [y:d:h:m:s]: 03:027:21:09:41
Block: 386854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798825 RingCT/type: yes/0
Extra: 0177469ba2790b083b2c81be7280537057bd9ca1a2c0432df3c62132a71395fb5e02110000000437cb3088000000000000000000

1 output(s) for total of 32.076906479000 dcy

stealth address amount amount idx
00: 07ecb79cf7f679344f6c239ef2b714415caf6e7730aea6e0f3e7bb97009bfaec 32.076906479000 780371 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": 386864, "vin": [ { "gen": { "height": 386854 } } ], "vout": [ { "amount": 32076906479, "target": { "key": "07ecb79cf7f679344f6c239ef2b714415caf6e7730aea6e0f3e7bb97009bfaec" } } ], "extra": [ 1, 119, 70, 155, 162, 121, 11, 8, 59, 44, 129, 190, 114, 128, 83, 112, 87, 189, 156, 161, 162, 192, 67, 45, 243, 198, 33, 50, 167, 19, 149, 251, 94, 2, 17, 0, 0, 0, 4, 55, 203, 48, 136, 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