Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7468d691c9a179c1e6c40b1065d7fe22a8a1cd74dff4d48680ab991fae301f

Tx prefix hash: d94036fb1007ccc3294a5c57c24e6a3f72c0d31ade29452daeccfb2c01acb759
Tx public key: 9cb6f8140de256647f6c20da08bd5f98a9831f8d6236e080c185c0786b301e24
Timestamp: 1736996134 Timestamp [UCT]: 2025-01-16 02:55:34 Age [y:d:h:m:s]: 00:340:12:53:21
Block: 1198311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240933 RingCT/type: yes/0
Extra: 019cb6f8140de256647f6c20da08bd5f98a9831f8d6236e080c185c0786b301e24021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83dbe4b0b5c1077700697acf01d798170b92f3a5df663b70f672e348e6d6da10 0.600000000000 1684934 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": 1198321, "vin": [ { "gen": { "height": 1198311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83dbe4b0b5c1077700697acf01d798170b92f3a5df663b70f672e348e6d6da10" } } ], "extra": [ 1, 156, 182, 248, 20, 13, 226, 86, 100, 127, 108, 32, 218, 8, 189, 95, 152, 169, 131, 31, 141, 98, 54, 224, 128, 193, 133, 192, 120, 107, 48, 30, 36, 2, 17, 0, 0, 0, 6, 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