Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3fd340d189f9cecc7351c32d1d0727736e3b3e5484bd0e7489cc4c6f2492af

Tx prefix hash: 2109a1d6db263af77562daded8ee17383aadc56c6bf241d59eb1740b5ef1fb64
Tx public key: c8ebf66b11a0f812fea15b20f7a24e3771ca9e5c108cd784fc6f672b47f22c56
Timestamp: 1730554613 Timestamp [UCT]: 2024-11-02 13:36:53 Age [y:d:h:m:s]: 00:021:20:48:44
Block: 1144975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15645 RingCT/type: yes/0
Extra: 01c8ebf66b11a0f812fea15b20f7a24e3771ca9e5c108cd784fc6f672b47f22c56021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0415a5b90bd0149fe615b78d802e6751e97677741cd63a47a30e07d58813e437 0.600000000000 1629330 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": 1144985, "vin": [ { "gen": { "height": 1144975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0415a5b90bd0149fe615b78d802e6751e97677741cd63a47a30e07d58813e437" } } ], "extra": [ 1, 200, 235, 246, 107, 17, 160, 248, 18, 254, 161, 91, 32, 247, 162, 78, 55, 113, 202, 158, 92, 16, 140, 215, 132, 252, 111, 103, 43, 71, 242, 44, 86, 2, 17, 0, 0, 0, 4, 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